-
Notifications
You must be signed in to change notification settings - Fork 120
chore: Migrate spec module to JSpecify annotations for null-safety #638
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
ehsavoie
commented
Feb 10, 2026
- Add @NullMarked to io.a2a.spec package
- Apply @nullable annotations to optional fields and parameters
- Move builder validation to build() methods using Assert.checkNotNullParam()
- Fix null-safety issues in RequestContext ID generation
- Add null checks for push notification configuration
- Simplify REST route handling for push notification configs
- Update tests to provide required MessageSendConfiguration
Summary of ChangesHello @ehsavoie, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request significantly improves the null-safety and robustness of the Highlights
Changelog
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request successfully migrates the spec module to JSpecify annotations for null-safety, aligning with the stated objectives. Key changes include applying @Nullable annotations to optional fields and parameters, moving builder validation to build() methods using Assert.checkNotNullParam(), and introducing necessary null checks in various parts of the codebase. The test updates reflect these null-safety changes, ensuring continued correctness. The simplification of REST route handling for push notification configurations is also a positive improvement.
server-common/src/main/java/io/a2a/server/agentexecution/RequestContext.java
Outdated
Show resolved
Hide resolved
dd576cd to
46bbd2b
Compare
kabir
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One small question
46bbd2b to
594c3c7
Compare
- Add @NullMarked to io.a2a.spec package - Apply @nullable annotations to optional fields and parameters - Move builder validation to build() methods using Assert.checkNotNullParam() - Fix null-safety issues in RequestContext ID generation - Add null checks for push notification configuration - Simplify REST route handling for push notification configs - Update tests to provide required MessageSendConfiguration Signed-off-by: Emmanuel Hugonnet <ehugonne@redhat.com>
594c3c7 to
fee347f
Compare